home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Games Collection 1
/
software vault.zip
/
software vault
/
CDR03
/
FALCUTIL.ZIP
/
FALCNR.ZIP
/
README.NOW
< prev
next >
Wrap
Text File
|
1992-09-13
|
4KB
|
95 lines
*** READ ME NOW! ***
NOW HEAR THIS! NOW HEAR THIS!
This program ONLY WORKS WITH FALCON VERSIONS 3.0d, 3.01, and any new
versions 100% compatible with those versions!!! It can be forced to
_run_ with Falcon 3.0, 3.0a, and 3.0c but it will DAMAGE your
campaign and squadron files. That isn't a possibility, it's a cold
hard fact.
This version incorporates a lateral scanning system that will look
for the version numbers in your FALCON3.EXE -- it should allow
FALCNR to be started if you have any beta or final version of 3.0D or
3.01.
If, however, the system can't find the version number, or finds a
keyword from an earlier/later version, you will get an error message
and be asked to confirm entry to FALCNR with the [Y] key. Falconer
will default to its 3.01-compatible mode.
DO NOT DO THIS unless you are sure you actually have 3.01 or a
later version which also works with FALCNR. Check with me via
CompuServe or Internet if you aren't sure...! (My addresses are in
the .DOC file.)
If you own the upcoming 3.0E patch from Spectrum Holobyte, you may
get a special error message telling you to use one of the command line
switches in order to tell Falconer how to work with the campaign files:
You may invoke Falconer with the command "FALCNR IHAVED" to force it
into 3.0D compatible mode and bypass the version scan, or use "FALCNR
IHAVE1" to force it into 3.01 compatible mode and bypass the version
scan. Assuming no totally new campaign file formats are introduced in
3.0E, one of these two options will work properly.
If you use Falconer in shell mode, and require a command line switch,
you must edit the F3.BAT batch file to invoke Falconer with the
correct switch -- i.e. change "FALCNR" to "FALCNR IHAVED" or "FALCNR
IHAVE1" in the batch file.
FSFORUM.SQN
If you would like to use the 386th, 387th, and 486th FSFORUM squadrons
and would ALSO like to see them appropriately named in F3, you must make
a backup of your SQDNAMES.STR file in your Falcon 3.0 directory, then
copy the provided file FSFORUM.SQN to SQDNAMES.STR. This will change
three of the original squadron's names to "386th, 387th, and 486th
FSFORUM."
CAUTIONS ABOUT YFIF3!
There is one file, called PILOT.BIN, which holds 50 pilot faces
that you select from while in F3. YFIF3, the Falconer .PCX file
merger, OVER-WRITES the faces in PILOT.BIN.
Falconer release 3 searches for a file called PILOT.ABK when
you first run it. If it does not find that file, PILOT.BIN will
be copied over to PILOT.ABK. This pretty much ensures that before
you start twiddling around with YFIF3, a duplicate of your
PILOT.BIN file exists.
You can restore all the original faces by using File..Restore Faces
at any time. Work on an individual face can be saved independently
to disk using the pilot import/export features.
LEGAL MUMBO JUMBO --- REQUIRED READING FOR FALCONER USERS!!!
This program is freeware. It may be copied freely and distributed
as long as it is not modified in any way, and this documentation
file is packaged with the executable program.
No guarantees are made as to the compatibility of this program with
Falcon 3.0. It has been tested thoroughly. However, remember that
the purpose of this program is to allow you to modify data that
Falcon 3.0 does not want modified! A combination of changes you
engineer via this program could conceivably destabilize a F3
campaign and thence the program, though I believe it is highly
unlikely. It is also possible that future upgrades of F3 may be
incompatible with this program.
But read this carefully and understand it:
THIS PROGRAM ALTERS FALCON 3.0 DATA. ANY DAMAGE TO YOUR SYSTEM OR
FILES, EITHER DIRECT, INCIDENTAL, OR CONSEQUENTIAL, WILL NOT BE THE
RESPONSIBILITY OF THE AUTHOR OF "FALCONER." ADDITIONALLY, NO
GUARANTEES ARE MADE CONCERNING SUPPORT OF THIS SOFTWARE. IF YOU
ARE NOT WILLING TO ACCEPT INCIDENTAL RISKS TO YOUR DATA AND CANNOT
ENSURE ITS SAFETY VIA BACKUPS, DO NOT USE THIS PROGRAM!
- Rob Heittman